The problem

RM pro has a firmware issue that causes it to return -7 ºC when we call check_sensors() around 22.9 and 23 ºC.

If we ignore the issue, we return unreliable data. If we add a conditional and raise an exception, we raise false positives (-7 ºC may be a valid temperature), and it would also flood the logs, this behavior is consistent.

The right place to fix this is the firmware, but we don't have access to it.

Proposed change

Add a conditional to the update manager and replace -7 with the previous temperature when the variation is bigger than 3 °C.

If we get -7 °C at startup, we return None, so the temperature will be unknown until we get a different value, from which it will be possible to determine whether the next -7 is valid or not.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes Multiple Broadlink Temp Sensors occasionally report 249 degC after upgrade to 116.x from 114.4 #42100
• This PR is related to issue: Incorrect temperature iobroker-community-adapters/ioBroker.broadlink2#32 Error reported on max temperature lprhodes/homebridge-broadlink-rm#319 Geofancy Zone support with style fixes #543
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.